Incident report generation from multimedia data capture

ABSTRACT

This disclosure describes an apparatus and system for classifying audio and video data captured by a portable recording device. The portable recording device may comprise a camera system enclosure that captures audio and video data that reflects a user’s point-of-view perception of their surroundings. The video and/or audio data may be transmitted in real-time, or near real-time, to a Central Multimedia Management (CMM) System at a Network Operations Center, or one or more mobile computing devices, via one or more networks. Alternatively, or additionally, the video and/or audio data may be stored within memory of the portable recording device. This disclosure further describes a CMM system that may act as a central repository of multimedia data from one or more portable recording device(s). The CMM system may further generate and assign incident report forms for each individual instance of real-time data that is recorded by a portable recording device.

RELATED APPLICATION

This application is a continuation of U.S. Application No. 17/179,908,filed on Feb. 19, 2021 and titled “Portable Recording Device forReal-Time Multimedia Streams,” now U.S. Pat. No. 11,516,427, issued onNov. 29, 2022; which is a continuation of U.S. Application No.16/677,545, filed on Nov. 7, 2019, entitled “Portable Recording DeviceMultimedia Classification System,” now U.S. Pat. No. 10,958,868, issuedon Mar. 23, 2021; which is a division of U.S. Application No.15/686,142, filed on Aug. 24, 2017, titled “Portable Recording DeviceMultimedia Classification System,” now U.S. Pat. No. 10,511,801, issuedon Dec. 17, 2019; which claims the benefit of U.S. Provisional Pat.Application No. 62/379,212, filed on Aug. 24, 2016, and titled,“Category Selector for Body Camera Data Classification,” which areherein incorporated by reference in their entireties.

BACKGROUND

Law enforcement agencies are increasingly equipping their lawenforcement officers with portable recording devices. Such lawenforcement agencies may have policies mandating that their lawenforcement officers use these portable recording devices to recordtheir interactions with the public, to better serve and protect thepublic from improper policing, as well as protect law enforcementofficers from false allegations of police misconduct. In some examples,law enforcement officers may use data recorded by a portable recordingdevice to annotate incident report forms. However, the task ofgenerating incident forms from individual instances of multimediacaptured by a portable recording device can be a laborious task thatrequires a significant time commitment from a law enforcement officer,detracting from their other official duties.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIGS. 1A and 1B illustrate a schematic view of a computing environmentthat facilitates an interaction between a portable recording device, acentral multimedia management system, and a mobile multimedia managementsystem.

FIG. 2 illustrates a block diagram of various components of a portablerecording device that facilitates a recording or a stream of real-timedata.

FIG. 3 illustrates a block diagram of various components of a CentralMultimedia Management (CMM) System of a Network Operations Center.

FIG. 4 illustrates a block diagram of various components of a mobilecomputing device that operates a Mobile Multimedia Management (MMM)application.

FIG. 5 illustrates an exemplary portable recording device.

FIG. 6 illustrates an additional, exemplary portable recording device.

FIG. 7 illustrates a process for capturing real-time data via a portablerecording device and transmitting the real-time data within a multimediadata packet to a computing device.

FIG. 8 illustrates a process for capturing real-time data via a portablerecording device and selectively broadcasting a live stream a computingdevice via a high-energy (i.e. secure) communication connection.

FIG. 9 illustrates a process of generating an incident report form thatcorresponds to a stream of real-time data captured by a portablerecording device.

FIG. 10 illustrates a process of generating and transmitting auser-modified multimedia data packet to a portable recording device, viaa MMM application operating on a mobile computing device.

DETAILED DESCRIPTION

This disclosure describes an apparatus and system for classifying audioand video data captured by a portable recording device. The portablerecording device may comprise a camera system enclosure that is worn ona user’s torso and may capture audio and video data that reflects auser’s point-of-view perception of their surroundings. In some examples,video and/or audio data may be transmitted by the portable recordingdevice in real-time to one or more computing devices, via one or morenetworks. Alternatively, or additionally, the video and/or audio datamay be stored within memory of the portable recording device.

Additionally, this disclosure further describes a portable recordingdevice with a category selector that is capable of assigning a categoryclassification to video and/or audio data that is being captured by theportable recording device. The category selector may take the form ofany switching mechanism that can toggle between one or more presetpositions. Each preset position may correspond to a particular categoryclassification. In a non-limiting example, category classifications maycorrespond to the roles and responsibilities of users that wear portablerecording devices. For example, the preset category classifications fora patrol officer may include speeding citations, traffic citations,motorist assist, emergency response, and/or so forth. Similarly,category classifications for detectives may include emergency response,arrest, assist another agency, and inspections. The purpose of assigninga category classification to captured video and/or audio data is toincrease the efficiency of evidence management and classification. Thatis, video and audio data that is transmitted by the portable recordingdevice to a Central Multimedia Management (CMM) system at a networkoperations center (NOC), or another mobile computing device, may betransmitted simultaneously with metadata classifying the data into acategory that corresponds with departmental evidence group policies.

In various examples, the central multimedia management (CMM) system mayact as a central repository of multimedia data from one or more portablerecording device(s) operated by law enforcement officers. Further, theCMM system may generate and assign incident report forms for eachindividual instance of real-time data that is recorded by a portablerecording device. By way of example, the CMM system may automaticallypopulate an incident report form using segmented portions of a real-timedata recording (i.e. real-time data may be segmented based on milestoneindicator metadata), along with metadata received from the portablerecording device. The metadata may relate to individual instances ofreal-time data or the portable recording device itself. For example, themetadata that relates to individual instances of real-time datarecordings may include a timestamp and/or a date stamp associated witheach instance of real-time data, or a GPS location of the portablerecording device at a point in time that the real-time data is captured.Additionally, or alternatively, the metadata may be derived from one ormore selections performed via the portable recording device, and mayinclude one or more of a category selection, a sub-category selection,or milestone indicator(s). Further, the metadata that relates to theportable recording device itself may include a device identifier or anassignment identifier of a law enforcement officer who is assigned tooperate the portable recording device.

Additionally, this disclosure further describes techniques that allowthe portable recording device to act as a portable wireless hotspot thatprovides a wireless communication connection to an authorized mobilecomputing device. In doing so, the mobile computing device, via themobile multimedia management (MMM) system, may initiate receipt ofmultimedia data packets from the portable recording device, and furthertransmit user-modified multimedia data packets to the portable recordingdevice. By way of example, consider a law enforcement officer operatinga portable recording device with internet access via atelecommunications network. In this example, the law enforcement officermay establish a secure communication connection with the mobilecomputing device via the telecommunications network associated with theportable recording device. In doing so, the MMM application, via themobile computing device, may initiate receipt of multimedia data packetsfrom the portable recording device. The MMM application may furthergenerate, via the mobile computing device, an incident report form thatis based on a stream of real-time data and corresponding metadataassociated with the multimedia data packet. In this instance, the lawenforcement officer may enter or adjust information within the incidentreport form, such as case identifiers, pertinent individual personalinformation (i.e. name, address, date of birth, and/or so forth),category classifications, sub-category classifications, milestoneindicator(s), audio annotations, text annotations, and/or so forth. Indoing so, the MMM application may generate user-modified metadata basedon the information entered or adjusted in creating the incident reportform. Further, the MMM application may generate a user-modifiedmultimedia data packet that aggregates the user-modified metadata withthe stream of real-time data and corresponding metadata that wasoriginally sent to the mobile computing device from the portablerecording device. The MMM application may further cause the mobilecomputing device to transmit the user-modified multimedia data packet tothe portable recording device, via the secure communication connection,to replace the original multimedia data packet stored on the portablerecording device. The purpose of doing so ensures that the user-modifiedmultimedia data packet is later uploaded from the portable recordingdevice to the CMM system, rather than to the multimedia data packet thatdoes not include the user input of data entries. In this way, the dataentries, annotations, and modifications, implemented by the assignedpersonnel, via the mobile computing device, are uploaded to the CMMsystem.

It is noteworthy that the terms “law enforcement officer” and “assignedoperator of the portable recording device” are used interchangeablythroughout this disclosure.

Further, the term “techniques,” as used herein, may refer to system(s),method(s), computer-readable instruction(s), module(s), algorithms,hardware logic, and/or operation(s) as permitted by the contextdescribed above and through the document. Example implementations areprovided below with reference to FIGS. 1 through to 9 .

FIG. 1A illustrates a schematic view of a computing environment 100 thatfacilitates an interaction between a portable recording device 102, acentral multimedia management (CMM) system 104, and the mobilemultimedia management (MMM) application 106 operating on a mobilecomputing device 108. The computing environment 100 may further includea law enforcement vehicle 110 operated by a law enforcement officer 112that is equipped with the mobile computing device 108. Further, themobile computing device 108 may communicate with the portable recordingdevice 102 via one or more network(s) 116.

In the illustrated example, the CMM system 104 may be part of a NetworkOperations Center (NOC) 114. The NOC 114 may be a command center that ispart of a law enforcement agency, or a facility that is operated by athird-party that is offering services to a law enforcement agency. TheCMM system 104 may operate on one or more distributed computingresource(s) 118. The one or more distributed computing resource(s) 118may include one or more computing device(s) 120(1)-120(N) that operatein a cluster or other configuration to share resources, balance load,increase performance, provide fail-over support or redundancy, or forother purposes. The one or more computing device(s) 120(1)-120(N) mayinclude one or more interfaces to enable communications with othernetworked devices, such as a portable recording device 102 or a mobilecomputing device 108 associated with a law enforcement vehicle 110, viaone or more network(s) 116. The one or more network(s) 116 may includepublic networks such as the Internet, private networks such as aninstitutional and/or personal intranet, or some combination of privateand public networks. The one or more network(s) 116 can also include anytype of wired and/or wireless network, including but not limited tolocal area network (LANs), wide area networks (WANs), satellitenetworks, cable networks, Wi-Fi networks, Wi-Max networks, mobilecommunications networks (e.g. 3G, 4G, and so forth), or any combinationthereof. Protocols for network communication, such as TCP/IP, may beused to implement a communication connection via the one or morenetwork(s) 116.

Further, the mobile computing device 108 may include any sort ofelectronic device, such as a cellular phone, a smartphone, a tabletcomputer, a personal computer (PC), a laptop computer, etc. The mobilecomputing device 108 may include output devices (e.g. a display screen)upon which data relating to incident report forms and real-time datarecordings may be displayed. The mobile computing device 108 may alsoinclude an input device (e.g. a keyboard or mouse) by which the lawenforcement officer 112 may enter information. The mobile computingdevice 108 may be equipped with a low-energy transceiver and ahigh-energy transceiver. For example, the low-energy transceiver may bea Bluetooth or an NFC transceiver, while the high-energy transceiver maybe a Wi-Fi transceiver. In some instances, the mobile computing device108 may be further equipped with a power port (e.g. a Universal SerialBus (USB) port, a Lightning port, etc.) that provides power andcommunication interfaces.

The portable recording device 102 may be worn by the law enforcementofficer 112 while performing official duties. The portable recordingdevice 102 may be a portable video recording device, a portable audiorecording device, or a portable multimedia recording device that recordsimage data (i.e. in-motion video image data or still-motion image data)and audio data via one or more sensors. The one or more sensors mayinclude microphones, video image sensors, and/or so forth. The portablerecording device 102 may include on-board memory that stores instancesof captured audio data, image data, or multimedia data, as real-timedata. The portable recording device 102 may be manually activated torecord real-time data by the law enforcement officer 112. For example,the portable recording device 102 may include an input interface (e.g.physical buttons, a gesture recognition mechanism, a voice activationmechanism) that enables the law enforcement officer 112 to start, stop,and/or pause the recording of the real-time data. In various examples,the real-time data may capture incidents, events, crimes, and/or soforth, that are of law enforcement or public interest as the lawenforcement officer 112 performs official duties.

FIG. 1B illustrates a schematic view of a computing environment 100 thatfacilitates an interaction between a portable recording device 102 and amobile computing device 108. The mobile computing device 108 may beassociated with a law enforcement vehicle 110 that is operated by a lawenforcement officer 112. Further, the mobile computing device 108 mayoperate the mobile multimedia management (MMM) application 106 thatinteracts with the portable recording device 102.

In the illustrated example, the portable recording device 102 may use alow-energy transceiver to form a low-energy (i.e. unsecured)communication connection 122 with the mobile computing device 108. Insome examples, the portable recording device 102 may broadcast aheartbeat signal that includes a device identifier of the portablerecording device. In one example, the portable recording device 102 maybroadcast the heartbeat signal continuously or based on a predeterminedschedule. The time interval associated with the predetermined schedulemay be one second, 10 seconds, or 30 seconds. Any time interval ispossible. For example, the portable recording device 102 may broadcastthe heartbeat signal every second.

In one example, the mobile computing device 108 may act as a Wi-Fiaccess point and the portable recording device 102 may act as a Wi-Ficlient. For example, following receipt of the heartbeat signal, themobile computing device 108 may transmit a device identifieracknowledgment message to the portable recording device 102 that causesthe portable recording device 102 to transmit authentication data 128 tothe mobile computing device 108. In response to verifying theauthenticity of the authentication data 128, the mobile computing device108 may transmit a secure connection settings data packet 130 to theportable recording device 102 via the low-energy (i.e. unsecured)communication connection 122. Upon receiving the secure connectionsettings data packet 130, the portable recording device 102 mayestablish a high-energy (i.e. secure) communication connection 124 withthe mobile computing device 108. Thus, in the case of a Wi-Ficonnection, the mobile computing device 108 may act as a Wi-Fi accesspoint and the portable recording device 102 may act as a Wi-Fi client.

In another example, the portable recording device 102 may act as a Wi-Fiaccess point and the mobile computing device 108 may act as a Wi-Ficlient. In this example, following receipt of the heartbeat signal, andverification of the authentication data 128 associated with the portablerecording device 102, the mobile computing device 108 may transmit anadditional acknowledgment message to the portable recording device 102that causes the portable recording device 102 to transmit a secureconnection settings data packet 130. Upon receiving the secureconnection settings data packet 130, the mobile computing device 108 mayestablish a high-energy (i.e. secure) communication connection 124 withthe portable recording device 102. Thus, in the case of a Wi-Ficonnection, the portable recording device 102 may act as a Wi-Fi accesspoint and the mobile computing device 108 may act as a Wi-Fi client.

In one example, the high-energy (i.e. secure) communication connection124 may be used by the mobile computing device 108 to send commands 132to the portable recording device 102. The commands 132 may configurecamera resolution, video buffer, buffering duration, pre-buffer audiomute, image stability, activation of GPS, and category/sub-categoryclassification identifiers associated with preset positions for thecategory selector of the portable recording device. In one example, thecommands 132 may initiate a file transfer of multimedia data packet(s)126 from the portable recording device 102, to the mobile computingdevice 108. In doing so, the mobile computing device 108 may generate anincident report form associated with the multimedia data packet(s) 126.The incident report form may include segmented portions of a real-timedata recording (i.e. real-time data may be segmented based on milestoneindicator metadata), along with metadata received from the portablerecording device 102. Further, a law enforcement officer 112 may modifythe incident report form, via the mobile computing device 108, toinclude audio annotations or text annotations. In doing so, the mobilecomputing device 108 may generate a user-modified multimedia data packet134 by aggregating the incident report form as additional metadata,along with the original content of respective multimedia data packet(s)126. The purpose of doing so is to ensure that any multimedia datapackets uploaded from the portable recording device 102 to the CMMsystem 104 include annotations and modifications made by the lawenforcement officer 112 via the mobile computing device 108.Alternatively, the exchange of multimedia data packets may be madebetween the mobile computing device 108 and the CMM system 104, inresponse to establishing a high energy (i.e. secure) communicationconnection between the mobile computing device 108 and the CMM system104.

It is noteworthy that the authentication process between the mobilecomputing device and the portable recording device may be based on theportable recording device being assigned to a law enforcement officerthat is operating the mobile computing device. In this example, the MMMapplication operating on the mobile computing device may have access toan assignment table maintained by the CMM system to ensure that a properassignment of the portable recording device is in place.

FIG. 2 illustrates a block diagram of various components of a portablerecording device that facilitates a recording or a stream of real-timedata. Further, the portable recording device 202 may be configured togenerate and assign metadata to individual instances of real-time data.The portable recording device 202 may be equipped with input/outputinterface(s) 204, network interface(s) 206, one or more sensor(s) 208,and a controller 210. Input/output interface(s) 204 may include outputinterfaces, such as a speaker, a vibrating mechanism, or a tactilefeedback mechanism. The input/output interface(s) 204 may also includeports for one or more peripheral devices, such as headphones orperipheral speakers. The input/output interface(s) 204 may further oneor more physical buttons/switches, gesture recognition mechanisms, avoice activation mechanism, or the like. By way of example, the one ormore buttons/switches may include an activation button, a mode button, acategory selector, or a connectivity wake-up button. The one or morebuttons/switches are discussed in more detail with reference to FIGS. 5and 6 .

Additionally, the one or more sensor(s) 208 may include a camera and amicrophone to capture video image data and audio data, and a GPS sensorto detect the geolocation of the portable recording device 202.

Further, the network interface(s) 206 may include any sort oftransceiver known in the art. The network interface(s) 206 may include aradio transceiver that performs the function of transmitting andreceiving radio frequency communications via an antenna. In addition,the network interface(s) 206 may also include a wireless communicationtransceiver and a near field antenna for communicating over unlicensedwireless Internet Protocol (IP) networks, such as local wireless datanetworks and personal area networks (e.g. Bluetooth or near fieldcommunication (NFC) networks). Further, the network interface(s) 206 mayinclude wired communication components, such as an Ethernet port or aUniversal Serial Bus (USB).

Moreover, the controller 210 of the portable recording device 202 mayinclude routines, program instructions, objects, and/or data structuresthat perform particular tasks or implement abstract data types. Thecontroller 210 may include one or more processor(s) 212 that areoperably connected to memory 214. In at least one example, the one ormore processor(s) 212 may be a central processing unit(s) (CPU),graphics processing unit(s) (GPU), both a CPU and a GPU, or any othersort of processing unit(s). Each of the one or more processor(s) 212 mayhave numerous arithmetic logic units (ALUs) that perform arithmetic andlogical operations as well as one or more control units (CUs) thatextract instructions and stored content from processor cache memory, andthen execute these instructions by calling on the ALUs, as necessaryduring program execution. The one or more processor(s) 212 may also beresponsible for executing all computer applications stored in thememory, which can be associated with common types of volatile (RAM)and/or nonvolatile (ROM) memory.

In some examples, memory 214 may include system memory, which may bevolatile (such as RAM), non-volatile (such as ROM, flash memory, etc.)or some combination of the two. The memory may also include additionaldata storage devices (removable ad/or non-removable) such as, forexample, magnetic disks, optical disks, or tape.

The memory 214 may further include non-transitory computer-readablemedia, such as volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer-readable instructions, data structures,program modules, or other data. System memory, removable storage, andnon-removable storage are all examples of non-transitorycomputer-readable media. Examples of non-transitory computer-readablemedia include, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transitorymedium which can be used to store the desired information.

In the illustrated example, the memory 214 may include an operatingsystem 216, a real-time data capture module 218, an activation module220, a metadata module 222, a multimedia data packet generation module224, a data transfer module 226, and a data store 228. The operatingsystem 216 may be any operating system capable of managing computerhardware and software resources.

Further, the real-time data capture module 218 may record real-time datacaptured via a camera and/or a microphone of the portable recordingdevice 202. The real-time data may be in the form of video data, audiodata, and/or multimedia data. Accordingly, the real-time data capturemodule 218 may include codecs, signal filters, coding functions, and/orerror correction functions that enable the real-time data capture module218 to generate digital data from camera and microphone signal inputs.

The activation module 220 may receive one or more commands from a CMMsystem or an MMM application. In one example, the activation module 220may repeatedly broadcast a heartbeat signal via a low-energycommunication transceiver to verify whether a current high-energycommunication connection is available. The heartbeat signal may includea device identifier of the portable recording device. Further, theactivation module 220 may transmit authentication data to a CMM systemor a MMM application, via a low-energy communication connection, inresponse to determining that a high-energy communication connection isavailable.

In another example, the activation module 220 may receive one or morecommands from the CMM system or MMM application that activates thereal-time data capture module 218 to capture and/or live stream ofreal-time data. The one or more commands may correspond to a start,stop, or pause command regarding a real-time data recording and/or livestreaming. The activation module 220 may also receive manual inputs thatstart, stop, or pause the recording and/or live streaming of real-timedata via physical buttons (i.e. activation button) of the portablerecording device. During live streaming, the real-time data capturemodule 218 may compress motion image data and/or audio data that iscaptured by the one or more sensor(s) 208 using a loss or losslesscompression (i.e. H.264, MPEG-4, etc.) for transmission to the CMMsystem or the MMM application, via the data transfer module 226. Inturn, the data transfer module 226 may relay the compressed live streamto the CMM system or the MMM application.

The metadata module 222 may tag the real-time data that is captured bythe real-time data capture module 218, with metadata. In some examples,the metadata may relate to the real-time data or the portable recordingdevice 202 itself. For example, the metadata that relates to thereal-time data may include a timestamp and/or a date stamp associatedwith each instance of real-time data, or a GPS location of the portablerecording device 202 at a point in time that the real-time data iscaptured. Additionally, or alternatively, the metadata may be derivedfrom one or more selections performed via the portable recording device202, and may include one or more of a category selection, a sub-categoryselection, or milestone indicator(s). By way of example, a categoryselection may correspond to “patrol officers,” “detectives,” “specialunits,” “assist another agency,” etc. Further, a sub-category selectionmay depend on the original category selection. For example, sub-categoryselections that depend on the “patrol officers” category selection mayinclude “speeding,” “traffic citation,” “motorist assist,” and/or”emergency response.” In another example, sub-category selections thatdepend on a “detectives” category selection may include “emergencyresponse,” “arrest,” “assist other agency,” or “inspection.” In yetanother example, sub-category selections that depend on a ”specialunits” category selection may include “arrest,” “assist another agency,”“inspection,” and/or “backup officer.” It is noteworthy that eachsub-category classification may have a further set of sub-sub-categoryclassifications. For example, an “arrest” sub-category classificationmay include “known suspect,” “unknown suspect,” or “resisting suspect.”Any number of sub-category classification levels (i.e. hierarchy ofclassification levels) is possible.

Moreover, the milestone indicator(s) may be captured by the lawenforcement officer pressing an activation button of the portablerecording device while recording a stream of real-time data. Themilestone indicator(s) are intended to flag a point in time during thestream of real-time data that the law enforcement officer, or assignedoperator of the portable recording device, has identified as beingpertinent and/or significant to the incident, and as such may beaddressed in detail by an audio annotation or text annotation within anensuing incident report form. By way of example, consider a lawenforcement officer, or assigned operator of the portable recordingdevice, may record a stream of real-time data for a traffic citation.The law enforcement officer may initiate a milestone indicator duringthe interaction at a point in time when the cited individual becomescombative, or argumentative. The law enforcement officer may flag thispoint in time as a pertinent and/or a significant milestone of theinteraction that may require additional audio or textual annotationswithin an incident report form.

Further, the metadata that relates to the portable recording device 202itself may include a device identifier or an assignment identifier of alaw enforcement officer who is assigned to operate the portablerecording device.

Additionally, the metadata module 222 may receive additional input ofdescriptive data for real-time data that is input by a law enforcementofficer, via a mobile computing device that operates a MMM application.The MMM application is described in further detail with reference toFIG. 4 . In one example, the descriptive data may include audioannotations and/or text annotations (i.e. officer commentaries) thatrelate to an instance of real-time data. In another example, thedescriptive data may include an incident identifier, an eventidentifier, a case number, an involved party name, and/or so forth.Alternatively, the law enforcement officer may provide a code word thatis pre-assigned to represent an incident, an event, or a case.

The multimedia data packet generation module 224 may generate amultimedia data packet by aggregating each instance of real-time datacaptured by the portable recording device with associated metadata. Anydescriptive data provided by a law enforcement officer via an MMMapplication may be aggregated within the multimedia data packet asmetadata.

The data transfer module 226 may be configured to transfer a multimediadata packet to one of a CMM system at a NOC or an MMM application thatis associated with a mobile computing device. The data transfer module226 may be configured such that the multimedia data packet may betransferred via an established high-energy (secure) connection with oneof the CMM system or MMM application.

The data store 228 may include one or more databases, such as relationaldatabases, object databases, and/or key-value databases that store data.In one example, the data store 228 may store the real-time data capturedby the portable recording device 202, along with associated metadata,and descriptive data input by a law enforcement officer.

FIG. 3 illustrates a block diagram of various components of a CentralMultimedia Management (CMM) System 302 of a Network Operations Center(NOC). The CMM system 302 may correspond to CMM system 104. Further, theCMM system 302 may act as a central repository of multimedia data fromone or more portable recording device(s) operated by law enforcementofficers. Further, the CMM system may generate and assign incidentreport forms for each individual instance of real-time data that isrecorded by a portable recording device.

In the illustrated example, the CMM system 302 may be coupled to aportable recording device via network interface(s) 304. The networkinterface(s) 304 may correspond to network interface(s) 206. In thisexample, the CMM system 302 may transmit one or more commands to aportable recording device via the network interface(s) 304, and furtherreceive multimedia data packets from a portable recording device.

Further, the CMM system 302 may include input/output interface(s) 306.The input/output interface(s) 306 may include any type of outputinterface known in the art, such as a display (e.g. a liquid crystaldisplay), speakers, a vibrating mechanism, or a tactile feedbackmechanism. Input/output interface(s) 306 also include ports for one ormore peripheral device(s), such as headphones, peripheral speakers, or aperipheral display. Further, the input/output interface(s) 306 mayfurther include a camera, a microphone, a keyboard/keypad, or atouch-sensitive display. A keyboard/keypad may be a push-buttonnumerical dialing pad (such as on a typical telecommunication device), amulti-key keyboard (such as a conventional QWERTY keyboard), or one ormore other types of keys or buttons, and may also include ajoystick-like controller and/or designated navigation buttons, or thelike.

In the illustrated example, the CMM system 302 may include one or moreprocessor(s) 308 operably connected to memory 310. The one or moreprocessor(s) 308 may correspond to the one or more processor(s) 212, andthe memory 310 may correspond to the memory 214. The memory 310 mayfurther include an operating system 312, an authentication module 314,an activation module 316, an assignment module 318, an incident reportform generation module 320, a data transfer module 322, and a data store324. The operating system 312 may be any operating system capable ofmanaging computer hardware and software resources.

Further, the authentication module 314 may receive, via a low-energy(i.e. secure) communication connection, authentication data from aportable recording device. Authentication data may include the deviceidentifier of the portable recording device, such as an electronicserial number (ESN), a globally unique identifier (GUID), an integratedcircuit card identifier (ICCID), or any other unique digital identifierstored in the portable recording device. In response to verifying theauthenticity of the authentication data, the authentication module 314may transmit a secure connection setting data packet to the portablerecording device. The secure connection settings data packet may includean access point identifier (i.e. Service Set Identifier (SSID)), thesecurity encryption scheme type, and an access point password. Uponreceipt of the secure connection settings data packet, the portablerecording device may initiate a high-energy (i.e. secure) communicationconnection with the CMM system. In some examples, the secure connectionsetting data packet may include computer-executable instructions thatautomatically associate the secure connection settings with aconnectivity wake-up button of the portable recording device, asdiscussed in more detail with reference to FIGS. 5 and 6 . In doing so,the authentication module 314 need only transmit the secure connectionsettings data packet once to the portable recording device. Following aninitial authentication process, the authentication module 314 mayinstead, transmit a signal to the portable recording device thatactivates (i.e. turns on) the connectivity wake-up button. In doing so,the portable recording device may establish a high-energy (i.e. secure)communication with the CMM system, based on the previously associatedsecure connection settings. It is noteworthy that the authenticationmodule 314 may selectively transmit a secure connection settings datapacket to a portable recording device, following an initialauthentication process, to ensure that the portable recording device isusing updated or up to date secure connection settings.

Additionally, the activation module 316 may receive a heartbeat signalthat is broadcast by a portable recording device. The heartbeat signalmay have been intended to determine whether a high-energy (i.e. secure)communication connection is available. In doing so, the activationmodule 316 may transmit an acknowledgment message to the portablerecording device that causes the portable recording device to transmitauthentication data, via a low-energy (i.e. unsecured) communicationconnection.

The activation module 316 may also transmit one or more commands to aportable recording device that are intended to initiate real-time datacapture and/or live stream of real-time data. In this example, the oneor more commands may correspond to a start, stop, or pause command of areal-time data recording and/or live streaming.

Moreover, the assignment module 318 may assign a portable recordingdevice to a law enforcement officer. Once a portable recording device isassigned to a law enforcement officer, the real-time data that isrecorded by the portable recording device from that point in time onwardis assigned to the law enforcement officer. In one example, theassignment module 318 may assign a portable recording device to a lawenforcement officer using an assignment table. The assignment table mayassociate a law enforcement officer identifier with a device identifierof a portable recording device. For example, a law enforcement officermay be issued with an NFC-tagged identification card, and each portablerecording device may be equipped with an NFC unit identifier. Thus, theNFC-tagged identification card may include an officer identifier thatidentifies the law enforcement officer. Accordingly, during a check-outprocess, an NFC unit identifier may be scanned with an NFC reader withina Network Operations Center. Subsequently, the NFC-tagged identificationcard of the law enforcement officer may be scanned with the NFC readerin a predetermined amount of time to associate the officer with theportable recording device. Thus, the association information may bestored in the assignment table.

In another example, the assignment module 318 may receive a user inputvia an input interface of the CMM system 302 that assigns a portablerecording device to a particular law enforcement officer. In thisexample, the assignment module 318 may record a user input of anassignment within the assignment table. In one example, a lawenforcement officer may securely log in to the CMM system 302 andprovide the assignment user input. In another example, the assignmentmay be performed by an administrator, at the back-end of the CMM system302.

Further, the incident report form generation module 320 mayautomatically generate an incident report form for individual instancesof multimedia data packets received from portable recording devices. Theincident report form generation module 320 may generate an incidentreport form by including a link to segmented portions of a real-timedata recording (i.e. real-time data may be segmented based on milestoneindicator metadata), along with information associated with the metadatareceived from the portable recording device. Further, a law enforcementofficer may enter or adjust information within the incident report form,such as case identifiers, pertinent individual personal information(i.e. name, address, date of birth, and/or so forth), categoryclassifications, sub-category classifications, milestone indicator(s),audio annotations, text annotations, and/or so forth. The incidentreport form generation module 320 may further provide access to aread-writable version of the incident report form to a computing deviceassociated with a law enforcement officer who was assigned to theportable recording device that captured the associated real-time data ata point in time that corresponds to the recording of the real-time data.By way of example, consider a first law enforcement officer, who wasassigned a portable recording device, recording the first instance ofreal-time data at the first point in time. At a later date, the portablerecording device may be re-assigned to a second law enforcement officer,and the second law enforcement officer may use the portable recordingdevice to record the second instance of real-time data. In this example,the incident report form generation module 320 may generate incidentreport forms for the first and second instances of real-time data.However, the incident report form generation module 320 may provide thefirst law enforcement officer with access to a read-writable version ofthe incident report form for the first instance of real-time data, basedon the recorded assignment at the point in time that the first instanceof real-time data was captured. Similarly, the incident report formgeneration module 320 may provide the second law enforcement officerwith access to a read-writable version of the incident report form forthe second instance of real-time data.

Additionally, the data transfer module 322 may be configured to initiatereceipt of, and receive multimedia data packets from, a portablerecording device. The data transfer module 322 may be configured suchthat multimedia data packets may be transferred via an established,high-energy (secure) communication connection with a portable recordingdevice. The multimedia data packets may include an aggregate ofreal-time data captured by a portable recording device along withassociated metadata.

Moreover, the data store 324 may include one or more databases, such asrelational databases, object databases, and/or key-value databases thatstore data. In one example, the data store 324 may store the real-timedata captured by one or more portable recording devices, along withassociated incident report forms, metadata, and any other additionaldescriptive data input provided by an assigned, law enforcement officer.The real-time data may be organized in the data store 324 according tocorresponding assigned identifiers, such as a case identifier, eventidentifier, law enforcement officer identifier, and/or so forth.

FIG. 4 illustrates a block diagram of various components of a mobilecomputing device 402 that operates a Mobile Multimedia Management (MMM)application 404. In some examples, a law enforcement officer may use theMMM application 404 to download a multimedia data packet that isassociated with real-time data captured by a portable recording deviceassigned to the law enforcement officer. In doing so, the lawenforcement officer may view the corresponding real-time data and/orgenerate an incident report form, based on the real-time data andassociated metadata within the multimedia data packet. Thus, the lawenforcement officer may annotate the incident report form by includingaudio annotations and/or text annotations via the mobile computingdevice operating the MMM application 404. In some examples, the audioannotations and/or text annotations may include descriptive data of anincident associated with the real-time data, an incident identifier, anevent identifier, a case number, an involved party name, and/or soforth. Alternatively, the law enforcement officer may provide a codeword that is pre-assigned to represent an incident, an event, or a case.

In the illustrated example, the MMM application 404 may furtheraggregate any descriptive data provided by the law enforcement officervia the mobile computing device, as additional metadata within auser-modified multimedia data packet. The MMM application 404 mayfurther cause the mobile computing device 402 to transmit theuser-modified multimedia data packet to the portable recording device.In this way, the incident report form and descriptive data provided bythe law enforcement officer via the mobile computing device may beuploaded to the CMM system at a later point in time when the portablerecording device is communicatively coupled to the CMM system via ahigh-energy (i.e. secure) communication connection. In some examples,the user-modified multimedia data packet may replace the originalmultimedia data packet on the portable recording device. In otherexamples, the user-modified multimedia data packet may be stored inconjunction with the original multimedia data packet.

In the illustrated example, the mobile computing device 402 may becoupled to a portable recording device via network interface(s) 406. Thenetwork interface(s) 406 may correspond to network interface(s) 206and/or 304. In this example, the mobile computing device 402 maytransmit one or more commands to a portable recording device via thenetwork interface(s) 406 and further transmit and receive multimediadata packets to and from a portable recording device. The mobilecomputing device 402 may further include input/output interface(s) 408.The input/output interface(s) 408 may correspond to the input/outputinterface(s) 306.

Additionally, the mobile computing device 402 may include one or moreprocessor(s) 410 operably connected to memory 412. The one or moreprocessor(s) 410 may correspond to the one or more processor(s) 212and/or 308, and the memory 412 may correspond to the memory 214 and/or310. The memory 412 may further include an operating system 414, anauthentication module 416, an activation module 418, an incident reportform generation module 420, a multimedia data packet generation module422, and a data transfer module 424. The operating system 414 may be anyoperating system capable of managing computer hardware and softwareresources. The authentication module 416 may correspond to theauthentication module 314 of the CMM system 302, the activation module418 may correspond to the activation module 316 of the CMM system 302,and the incident report form generation module 420 may correspond to theincident report form generation module 320 of the CMM system 302. It isnoteworthy that the authentication module 416 may further determinewhether the portable recording device is properly assigned to the lawenforcement officer that is operating the mobile computing device 402.In this instance, the authentication module 416 may access an assignmenttable maintained by the assignment module 318 of the CCM system 302.Without a proper assignment, the authentication module 416 may notestablish a secure communication connection with the portable recordingdevice.

Further, the multimedia data packet generation module 422 may generateuser-modified multimedia data packets by modifying multimedia datapackets received from a portable recording device. The user-modifiedmultimedia data packets may include any user modifications to thereal-time data, and/or incident report forms generated via the mobilecomputing device 402. The incident report forms may be included withinthe user-modified multimedia data packets as additional metadata.

Moreover, the data transfer module 424 may be configured to initiatereceipt of, and receive multimedia data packets from, a portablerecording device. The multimedia data packets may include an aggregateof real-time data captured by a portable recording device along withassociated metadata. Additionally, the data transfer module 424 may befurther configured to transmit user-modified multimedia data packets tothe portable recording device that includes incident report forms asadditional metadata. The data transfer module 424 may be configured totransmit and receive multimedia data packets via an established,high-energy (secure) communication connection with a portable recordingdevice.

FIG. 5 illustrates an exemplary portable recording device 502. In theillustrated example, the portable recording device 502 may also includea camera 504 for capturing video image data, and a microphone 506 forcapturing audio and a speaker 508 for emitting audio. In some examples,the portable recording device 502 may also include a connectivity wakeupbutton 510 to selectively turn on and off wireless connectivity betweenthe portable recording device 502 and one or more computing device(s)that are communicatively coupled via one or more network(s), such as aCSS system or a MSS system.

In the illustrated example, the portable recording device 502 includes acategory selector that comprises a category wheel 512. The categorywheel 512 may include an indicator tab 514 that can align with presetradial position(s) 516 on a front face of the portable recording device502. In some examples, the indicator tab 514 may be configured to stopat a predetermined number of preset radial position(s) 516. Each of thepreset radial position(s) 516 may correspond to a categoryclassification that a user may assign to video and/or audio datacaptured by the portable recording device 502.

In one example, a user may use the category selector to assign acategory classification prior to capturing the real-time video and/oraudio data. In other examples, the user may use the category selector toselect a category classification while the video and/or audio data isbeing captured. Alternatively, a category classification may be assignedwithin a predetermined time period after the video and/or audio data hasbeen captured. In each of these instances, once the video and/or audiodata has been captured, a controller within the portable recordingdevice 502 may execute software instructions that associate the videoand/or audio data with metadata that corresponds to the categoryclassification. In some examples, the category selector may be used tofurther assign a sub-category classification to captured real-time data,as discussed in further detail below.

In an alternative embodiment, the category selector may include multiplecategory wheels, such as a second category wheel inset within the firstcategory wheel. The second category wheel may be configured in a similarmanner to the first category wheel, such that it may include anindicator tab that signposts a radial position of the wheel relative tothe front-facing surface of the portable recording device 502. Eachradial position of the second category wheel may correspond to asub-category classification that depends on the category classificationof the first wheel. For example, a user may turn a first category wheelto align the indicator tab with a radial position assigned to ‘trafficcitation.’ The user may then turn the second category wheel to a radialposition assigned to a sub-classification of ‘stop sign infraction.’ Inanother example, a user may turn the first category wheel to align theindicator tab with a radial position assigned to ‘assist anotheragency.’ Further, the second category wheel may be turned to align witha preset radial position assigned to the ‘fire department.’ In yetanother example, a user may turn the first category wheel to align theindicator tab with a radial position assigned to ‘detective.’ Further,the second category wheel may be turned to align with a preset radialposition assigned to ‘arrest.’

In the illustrated example, the portable recording device 502 mayfurther include a mode button 518. The mode button 518 may togglebetween a normal and covert configuration. A normal configuration mayindicate that the portable recording device 502 may emit audibleinformation. A covert configuration may selectively mute audible outputand increase emit haptic output.

Additionally, the portable recording device 502 may include anactivation button 520. The activation button 520 may be configured tocause the portable recording device 502 to perform one or more actionsthat depend on a present configuration of the portable recording device502. For example, the one or more actions may include starting andstopping the capture of video and/or audio data, marking a point ofinterest while video and/or audio data is being captured, or confirminga selection made by a user while configuring the portable recordingdevice 502. To assist a user of the portable recording device 502, theportable recording device 502 may include a speaker that emits anaudible request for information and/or an audible confirmation of inputmade by a user. By way of example, the portable recording device 502 maybe configured to audibly annunciate each category classification as auser (i.e. law enforcement officer) turns a category selector (i.e.category wheel) to align with each preset radial position. Further, theportable recording device 502 may be configured to select a categoryclassification based on the user pressing the activation button 520after aligning the category selector with a preset radial position. Indoing so, the portable recording device 502 may audibly confirm theselected category classification.

Further, the portable recording device 502 may be further configured toaudibly request a sub-classification following the selection of acategory classification. For example, the user may, once again, turn thecategory wheel 512 to align the indicator tab 514 of the category wheel512 with a particular preset radial position. In doing so, the portablerecording device 502 may audibly annunciate each categorysub-classification that corresponds to the preset radial position(s) 516that aligns with the indicator tab 514 of the category wheel 512.Further, the portable recording device 502 may audibly confirm aselection of a sub-category classification in response to the userpressing the activation button 520 after having aligned to the indicatortab 514 of the category wheel 512 with a particular preset radialposition. In some examples, the portable recording device 502 may beconfigured to forgo a sub-category selection in response to a lack ofuser input for a predetermined time interval, following an audibleprompt to select a sub-category classification.

In various examples, the activation button 520 may be used to performone or more actions. The one or more actions may correspond touser-initiated actions, such as initiating the capture of real-time data(i.e. video image data and/or audio data) by the portable recordingdevice 502, initiating a category selection, or sub-category selection,to assign to real-time data, aggregating a milestone indicator withinthe stream of real-time data, or terminating the capture of real-timedata. The selection of one or more actions may be based at least in parton the input form of user actuation of the activation button 520. Useractuation of the activation button 520 may correspond to a double-click,single-click, long-click, or a short-click. A long-click may correspondto a case in which the activation button 520 is pressed and held for apredetermined period of time, and a short-click corresponds to a case inwhich the activation button 520 is pressed and held for less than thepredetermined period of time. Although not limited as such, thepredetermined time may be long enough so that a user can make ashort-click conveniently, but not so long that the user must waitexcessively for the long-click to be recognized.

By way of example, the portable recording device 502 may be configuredsuch that a double-click of the activation button 520 may initiate thecapture of the real-time data, whereas, a long, double-click of theactivation button 520 may aggregate a milestone indicator within thestream of real-time data. In yet another example, a short, double-clickof the activation button 520 may indicate confirmation of a selectionmade by a user (i.e. category or sub-category selection, initiating orterminating the capture of real-time data). Any input form of useractuation (i.e. double-click or single-click, and/or a short-click orlong-click) may be assigned to any user-initiated action performed bythe portable recording device 502.

FIG. 6 illustrates an additional exemplary portable recording device602. In this example, the category selector may comprise a slideindicator tab 604, rather than a category wheel 512, as illustrated inFIG. 5 . In the illustrated example of FIG. 6 , rather than turning acategory wheel 512 to align an indicator tab 514 with preset position(s)606, a slide indicator tab 604 may be manually slid within an elongatedslot 608. The elongated slot 608 may include a predetermined number ofpreset position(s) 606 that each correspond to a category orsub-category classification. Each one of the preset position(s) 606 maybe mechanically configured to stop the slide indicator tab 604 as itpasses. Note that the slide indicator tab 604 configuration may causethe activation button 610 to be offset from its original position shownin FIG. 5 .

Further, the activation button 610, mode button 612, connectivity wakeupbutton 614, microphone 616, speaker 618, and camera 620, substantiallycorrespond to the activation button 520, mode button 518, connectivitywakeup button 510, microphone 506, speaker 508, and camera 504.

FIGS. 7, 8, 9, and 10 present processes 700, 800, 900, and 1000 thatrelate to operations of the portable recording device and central/mobilemultimedia management systems. Each of the processes 700, 800, 900, and1000 illustrate a collection of blocks in a logical flow chart, whichrepresents a sequence of operations that can be implemented in hardware,software, or a combination thereof. In the context of software, theblocks represent computer-executable instructions that, when executed byone or more processors, perform the recited operations. Generally,computer-executable instructions may include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order and/or in parallel to implement the process. Fordiscussion purposes, the processes 700, 800, 900, and 1000 are describedwith reference to the computing environment 100 of FIG. 1 .

FIG. 7 illustrates a process of capturing real-time data via a portablerecording device and transmitting the real-time data within a multimediadata packet to a computing device.

At 702, the portable recording device may capture, via one or moresensors, a stream of real-time data. The stream of real-time data mayinclude video image data and audio data that reflects a user’spoint-of-view perception of their surroundings.

At 704, the portable recording device may determine metadata associatedwith the stream of real-time data, based at least in part on useractuation of the portable recording device. For example, the metadatamay include a category classification and sub-category classification ofthe real-time data, along with one or more milestone indicator(s). Theone or more milestone indicator(s) may correspond to points in time,during the stream of real-time data, that have been identified, by a lawenforcement officer or assigned operator of the portable recordingdevice, as being pertinent and/or significant to the incident, and assuch may be addressed in detail by an audio annotation or textannotation within an ensuing incident report form.

At 706, the portable recording device may generate a multimedia datapacket that includes a recording of the stream of real-time data andassociated metadata. The associated metadata may include one or more ofa category classification of the stream of real-time data, asub-category classification, a timestamp and a date stamp associatedwith the capture of the real-time data, a GPS location of the portablerecording device at a point in time that the real-time data wascaptured, or one or more milestone indicator(s) associated with pointsin time during the real-time data.

At 708, the portable recording device may transmit, via a securecommunication connection, the multimedia data packet to a computingdevice. In one example, the computing device may correspond to a centralmultimedia management system within a network operations center. Inanother example, the computing device may be a mobile computing deviceof a law enforcement vehicle that operates a mobile multimediamanagement application.

FIG. 8 illustrates a process of capturing real-time data via a portablerecording device and selectively broadcasting a live stream a computingdevice via a high-energy (i.e. secure) communication connection.

At 802, the portable recording device may capture, via one or moresensors, a stream of real-time data. The stream of real-time data mayinclude video image data and audio data that reflects a law enforcementofficer’s point of view perception of their surroundings.

At 804, the portable recording device may determine the availability ofa secure communication connection between the portable recording deviceand a computing device. In one example, the portable recording devicemay search for a secure communication connection by transmitting aheartbeat signal on a continuous basis or based on a predeterminedschedule. The heartbeat signal may comprise a device identifierassociated with the portable recording device.

At 806, the portable recording device may determine that a securecommunication connection with a computing device is not available.Therefore, the portable recording device may store a recording of thestream of real-time data within a data store of the portable recordingdevice.

At 808, the portable recording device may determine that a securecommunication connection is available. More specifically, the portablerecording device may receive a device identifier acknowledgment messagethat causes the portable recording device to transmit authenticationdata to the computing device via a low-energy (i.e. unsecuredcommunication connection). In turn, the portable recording device mayreceive, from the computing device, a secure connection setting datapacket that includes settings data for the portable recording device toestablish a high-energy (i.e. secure) communication connection.

Further, the portable recording device may receive, from the computingdevice, a command to selectively broadcast in real-time, the stream ofreal-time data to the computing device. In response, the portablerecording device may broadcast the stream of real-time data via thehigh-energy (i.e. secure) communication connection.

At 810, the portable recording device may transmit, via the high-energy(i.e. secure) communication connection, a multimedia data packet at aconclusion of the stream of real-time data. The multimedia data packetmay include a recording of the stream of real-time data, along withassociated metadata.

FIG. 9 illustrates a flow diagram of a process for generating anincident report form that corresponds to a stream of real-time datacaptured by a portable recording device. The incident report form may begenerated by a central multimedia management (CMM) system.

At 902, the CMM system may retrieve, via a secure communicationconnection, a multimedia data packet from a portable recording device.The multimedia data packet may include a stream of real-time data andassociated metadata.

At 904, the CMM system may generate an incident report form thatcorresponds to the stream of real-time data and associated metadata. Forexample, the computing device may automatically populate an incidentreport form using segmented portions of a real-time data recording (i.e.real-time data may be segmented based on milestone indicator metadata),along with metadata received from the portable recording device. By wayof example, the computing device may automatically populate data such asa category classification, sub-category classification, milestoneindicators, GPS location data of the portable recording device at apoint in time that the real-time data was captured, and time stampand/or date stamp data associated with the real-time data.

At 906, the CMM system may determine whether the metadata within themultimedia data packet includes one or more milestone indicators.Milestone indicator(s) are generated by the law enforcement officer bypressing an activation of the portable recording device while recordinga stream of real-time data. The milestone indicator(s) are intended toflag a point in time during the stream of real-time data that the lawenforcement officer has identified as being pertinent and/or significantto the incident, and as such may be addressed in detail within anincident report form.

At 908, the CMM may determine that the metadata within the multimediadata packet includes one or more milestone indicators. In doing so, theCMM system may generate one or more segmented portion(s) of thereal-time data that correlate with the one or more milestoneindicator(s). The time interval for each segmented portion maycorrespond to a predetermined time interval, or a time period until anext milestone indicator or a combination of both. By way of example,consider a multimedia data packet that includes a stream of real-timedata along with corresponding metadata that includes two milestoneindicators. In one example, the CMM system may generate three-segmentedportions of the real-time data, based on the milestone indicators. Afirst segmented portion may commence with the beginning of the stream ofreal-time data until the first milestone indicator; the second segmentedportion may span between the first milestone indicator and the secondmilestone indicator; and, a third segmented portion may span between thesecond milestone indicator and the end of the stream of real-time data.In another example, the CMM system may generate two segmented portionsthat each span a predetermined time interval after a milestoneindicator.

At 910, the CMM system may generate and merge a link to each of the oneor more segmented portion(s) of the real-time data within the incidentreport form. Further, the CMM system may configure the incident reportform to permit a law enforcement officer, or authorized personnel, toprovide an audio annotation or text annotation that relates to eachmilestone indicator. In this way, the incident report form may include adescription of why the law enforcement officer determined a point intime during an incident was pertinent or significant to the recordedinteraction, as well as a recording of the corresponding segmentedportion of the real-time data.

At 912, the CMM system may provide access to a read-writable version ofthe incident report form to a computing device associated with anassigned law enforcement officer, or other assigned personnel. In someexamples, the read-writable version of the incident report form may berestricted to the law enforcement officer that was assigned the portablerecording device at the time the real-time data was captured. In someexamples, the CMM system may determine an assignment of the portablerecording device based at least in part on an assignment table thatcorrelates identifiers of law enforcement officers, or otherwiseauthorized personnel, with device identifiers of portable recordingdevices.

Referring back to 906, the CMM system may determine that the multimediadata packet does not include milestone indicators. In doing so, the CMMsystem may provide access to a read-writable version of the incidentreport form to a computing device associated with an assigned lawenforcement officer, or other assigned personnel.

FIG. 10 illustrates a process of generating and transmitting auser-modified multimedia data packet to a portable recording device, viaa MMM application operating on a mobile computing device.

At 1002, the mobile computing device may establish a securecommunication connection with a portable recording device. In oneexample, the portable recording device may act as a Wi-Fi access pointand the mobile computing device may act as a Wi-Fi client. In anotherexample, the mobile computing device may act as a Wi-Fi access point,and the portable recording device, as a Wi-Fi client.

At 1004, the mobile computing device may receive, from a portablerecording device, a multimedia data packet that includes a stream ofreal-time data. In various examples, the mobile computing device may beassociated with a law enforcement vehicle that is operated by a lawenforcement officer assigned to operate the portable recording device.

At 1006, the mobile computing device, via an MMM application, maygenerate an incident report form that corresponds to the stream ofreal-time data and corresponding metadata. In some examples, theincident report form may include information derived from the portablerecording device, such as category classifications, sub-categoryclassifications, and one or more milestone indicator(s).

At 1008, the mobile computing device, via the MMM application, mayreceive a user input of data entries that enter or adjust informationwithin the incident report form. The user input may include caseidentifier, pertinent individual personal information (i.e. name,address, date of birth, and/or so forth), category classifications,sub-category classifications, one or more milestone indicator(s), audioannotations, text annotations, and/or so forth.

At 1010, the mobile computing device, via the MMM application, maygenerate user-modified metadata based on the information entered oradjusted in creating the incident report form. In some examples, theuser-modified metadata may include information that is different fromthe metadata that was included in the original multimedia data packetsent from the portable recording device.

At 1012, the mobile computing device, via the MMM application, maycreate a user-modified multimedia data packet by aggregating theuser-modified metadata with the stream of real-time data andcorresponding metadata that was originally sent to the mobile computingdevice from the portable recording device.

At 1014, the mobile computing device, via the MMM application, maytransmit the user-modified multimedia data packet to the portablerecording device, via the secure communication connection. In someexamples, the user-modified multimedia data packet may replace themultimedia data packet that was originally sent by the portablerecording device. The purpose of doing so is to ensure that theuser-modified multimedia data packet is later uploaded from the portablerecording device to the CMM system, rather than the multimedia datapacket that does not include the user input of data entries. In thisway, the user inputs of data entries are uploaded to the CMM system.

Conclusion

Although the subject matter has been described in language specific tofeatures and methodological acts, it is to be understood that thesubject matter defined in the appended claims is not necessarily limitedto the specific features or acts described herein. Rather, the specificfeatures and acts are disclosed as exemplary forms of implementing theclaims.

What is claimed:
 1. A system, comprising: one or more processors; memorycoupled to the one or more processors, the memory including one or moremodules that are executable by the one or more processors to: obtain amultimedia data packet that includes an individual instance of real-timedata captured by a portable recording device; generate an incidentreport form that corresponds to the real-time data for the individualinstance of real-time data that is captured by the portable recordingdevice; and automatically populate the incident report form with atleast some of the real-time data.
 2. The system of claim 1, wherein thegeneration of an incident report form is automatic for the individualinstance of real-time data.
 3. The system of claim 1, wherein thereal-time data automatically populated in the incident report formincludes data segmented based on one or more milestone indicators. 4.The system of claim 1, wherein the real-time data automaticallypopulated in the incident report form includes metadata received fromthe portable recording device.
 5. The system of claim 4, wherein themetadata includes one or more category selections.
 6. The system ofclaim 1, wherein the automatically populated incident report form isread-writable to receive annotations from an operator.
 7. The system ofclaim 1, wherein the generation of an incident report form includeslinking to segmented portions of a real-time data recording.
 8. Thesystem of claim 1, wherein the one or more modules are furtherexecutable by the one or more processors to: obtain a plurality ofmultimedia data packets that include respective individual instances ofreal-time data captured by the portable recording device; generate anincident report form that corresponds to the real-time data for eachindividual instance of real-time data that is captured by the portablerecording device; and automatically populate the incident report formswith at least some of the real-time data corresponding to the individualinstances, respectively.
 9. A computer-implemented method, comprising:obtaining a plurality of multimedia data packets that include respectiveindividual instances of real-time data captured by the portablerecording device; generating an incident report form that corresponds tothe real-time data for each individual instance of real-time data thatis captured by the portable recording device; and automaticallypopulating the incident report forms with at least some of the real-timedata corresponding to the individual instances, respectively.
 10. Themethod of claim 9, wherein the generation of an incident report form isautomatic for each individual instance of real-time data.
 11. The methodof claim 9, wherein the real-time data automatically populated in theincident report forms includes data segmented based on one or moremilestone indicators.
 12. The method of claim 9, wherein the real-timedata automatically populated in the incident report forms includesmetadata received from the portable recording device.
 13. The method ofclaim 12, wherein the metadata includes one or more category selections.14. The method of claim 9, wherein the automatically populated incidentreport forms are read-writable to receive annotations from an operator.15. The method of claim 9, wherein the generation of an incident reportform includes linking to segmented portions of a real-time datarecording.
 16. One or more non-transitory computer-readable media ofstoring computer-executable instructions that when executed on one ormore processors, cause the one or more processors to perform actscomprising: obtaining a plurality of multimedia data packets thatinclude respective individual instances of real-time data captured by aportable recording device; generating an incident report form thatcorresponds to the real-time data for each individual instance ofreal-time data that is captured by the portable recording device; andautomatically populating the incident report forms with at least some ofthe real-time data corresponding to the individual instances,respectively.
 17. The one or more non-transitory computer-readable mediaof claim 16, wherein the generation of an incident report form includeslinking to segmented portions of a real-time data recording.
 18. The oneor more non-transitory computer-readable media of claim 16, wherein thereal-time data automatically populated in the incident report formsincludes data segmented based on one or more milestone indicators. 19.The one or more non-transitory computer-readable media of claim 16,wherein the generation of an incident report form is automatic for eachindividual instance of real-time data.
 20. The one or morenon-transitory computer-readable media of claim 16, wherein theautomatically populated incident report forms are read-writable toreceive annotations from an operator.